Configuring the DBMS

The Laserfiche Workflow Server and Subscriber require a DBMS to store data. They can share the same database or each use separate databases, but the database(s) should not be the same one used by a Laserfiche repository.

Before configuring the Workflow Server or Subscriber, ensure you have performed the following DBMS setup tasks. The tasks differ depending on which type of DBMS you are using.

Microsoft SQL Server

Ensure the database server is available to the Workflow Server and Subscriber machine(s). You do not need to manually create any new databases, as the Workflow Server and Subscriber Configuration Utilities will create these for you.

Oracle Database

Perform the following tasks:

• Ensure the database server is available to the Workflow Server and Subscriber machine(s).
• Install the Oracle Database Client on the Workflow Server and Subscriber machine(s). Ensure you install a version of the Client that includes TNS configuration, so that you can use the Oracle Net Configuration Assistant to configure the machine(s) hosting the Workflow Server/Subscriber to communicate with the Oracle server. For more information, see the Oracle Database documentation for instructions on connecting to an Oracle database from a local or a remote machine.

  Note: If you're using a 32-bit version of the Workflow Server or Subscriber, install the 32-bit version of the Oracle Client. Alternatively, if you're using a 64-bit version of the Workflow Server or Subscriber, install a 64-bit version of the Oracle Client.

• Create a new Oracle user/schema for the Workflow Server/Subscriber to use. The Workflow Server and Subscriber require a dedicated Oracle user/schema. These two components can share the same user/schema, or use separate users/schemas. At minimum, the user(s)/schema(s) should be granted the following roles/privileges:
  
  
  • CONNECT
  • RESOURCE
  • CREATE PROCEDURE
  • CREATE TABLE
  • CREATE VIEW

    Note: We recommend that Oracle privileges be granted directly to the Oracle user(s) associated with the Workflow Server/Subscriber, rather than through roles.

    Note: We recommend associating the Oracle database user(s) for the Workflow Server/Subscriber with a unique default tablespace that is separate from all other users.

    Note: The Oracle user account(s) used by the Workflow Server/Subscriber must have the INSERT, UPDATE, DELETE, and SELECT object privileges on all Workflow Server/Subscriber tables. The Workflow Server/Subscriber does not query tables outside of the Oracle data dictionary or the Oracle schema containing the Workflow Server/Subscriber data.